Method for combining unified matters in personal workspace and system using the same

ABSTRACT

A method for combining unified matters in a personal workspace and a system using the method are provided. The method includes the following steps. Firstly, at least one matterizer is provided to the personal workspace, wherein at least one unified information unit corresponding to at least one original information and/or at least one unified tool corresponding to at least one original tool is acquired from at least one information source via the at least one matterizer. Then, the at least one unified information unit and/or the at least one unified tool is provided to the personal workspace via the at least one matterizer. Then, through the at least one unified tool and/or the at least one unified information unit, a task is performed.

CROSS-REFERENCE TO RELATED APPLICATION

This application is continuation-in-part application of U.S. patentapplication Ser. No. 14/325,466, field Jul. 8, 2014 and herebyincorporates the content of this application by reference.

FIELD OF THE INVENTION

The present invention relates to a method for combining unified mattersin a personal workspace and a system using the method.

BACKGROUND OF THE INVENTION

Currently, many websites, operation systems or applications are rapidlydeveloped and become increasingly popular. These websites, systems andapplications provide convenience and changes for users but also bringproblems to the users because they are independent and incompatible withone another. In other words, the software vendors individually developwebsites, systems or applications which do not share a unifiedmechanism. As a result, different operation systems and applicationscannot cooperatively operate even with respect to data or tasks of thesame class. Therefore, the users need to open many working interfaces ofthe applications and use specific functions or services of them forperforming a task at present. Since there is no unified workspace tointegrate these applications, it is complicated, inefficient and eveninfeasible for the users to perform the task.

For example, a user can use Photoshop or PhotoImpact to complete animage processing task. PhotoImpact provides a simple module for the userto easily process an image, and Photoshop provides a professional toolfor advanced processing. If the user wants to apply a specific functionor tool of Photoshop and a specific function or tool of PhotoImpact toprocess the image at the same time, the user needs to respectivelyoperate Photoshop and PhotoImpact at present. Although these twoapplications can be applied in the same operation system, the tools ofPhotoImpact are not allowed to be applied into the interface ofPhotoshop. In general, the tools or functions of the currentapplications are unable to be applied mutually. The user cannot use asingle working environment or workspace to access or apply all of thefunctions or services of these applications. Therefore, the independenceand incompatibleness of these websites, operation systems andapplications block the freedom of the data/information exchange and theutilization of the functions or tools.

At present, a user can obtain much data or information from differentinformation sources such as website, cloud storage, or computer device.These information sources have standalone operation interfaces,respectively. Therefore, these data or information are restricted bythese standalone interfaces and are not easy or free for the user totransfer, access, or integrate. In the above situation, it istroublesome for the user in performing the work to process data orinformation which are scattered in various information sources. For thisreason, the user may need a workspace to unify these data or informationfrom the different information sources, and to provide an interface tointegrate and process these data or information efficiently.

In addition, the updated software versions in the operation systems alsomake trouble to a user. Because a current operation system only permitsone software version for each application, the user must choose onesoftware version to use. Although the updated software provides a newand convenient function or service to the user, some users may stillprefer to use the function or service of the old version because of somereasons (e.g., using habits). However most software vendors once providethe function or service of the new version, they will stop providingfunction or service of the old version. Therefore, the users are unableto freely choose the functions of the old versions they likes. Thus, theuser needs a workspace which allows the collaborative operation of manyservices supported by different software versions.

Accordingly, what is needed is a unified workspace that permits anyapplication or service of the different websites, operation systems orapplications to be performed and provides a user with a free arrangementmechanism of these applications or services to create a personal workingenvironment.

SUMMARY OF THE INVENTION

As mentioned above, the independence and incompatibleness of thewebsites, operation systems and applications block the freedom of thedata/information exchange. For solving these drawbacks, the presentinvention provides a method for combining unified matters in a personalworkspace and a system using the method.

In accordance with an aspect of the present invention, there is provideda system for combining unified matters in a personal workspace. Thesystem includes a processing unit for arranging at least one informationimporter and at least one unified tool in a personal workspace via aunified script and providing at least one unified information unit tothe personal workspace through the at least one information importer.Each unified information unit is produced by modeling an originalinformation of a first information source with a first unified datamodel, and basic attributes of each unified information unit include atype of the original information and a link indicating where theoriginal information is located. Each unified tool is produced bymodeling an original tool of a second information source with a secondunified data model, and basic attributes of each unified tool include atype of the original tool and a link indicating where the original toolis located. If the original tool is compatible with a workingenvironment of the personal workspace, the corresponding unified tool isdirectly produced according to the type of the original tool and thelink indicating where the original tool is located. If the original toolis incompatible with the working environment of the personal workspace,the unified tool is indirectly produced via an adapter and/or a softwaredevelopment kit (SDK) of the original tool to drive the original tool.The adapter provides an interface implementation compatible with thepersonal workspace. The processing unit accesses or controls the atleast one unified information unit to perform a task through the atleast one unified tool. When the at least one unified tool of thepersonal tool accesses or controls the at least one unified informationunit to perform the task, the at least one corresponding original toolaccesses or controls the at least one corresponding originalinformation.

In an embodiment, the unified script is used as an intermediate languagein the personal workspace.

In an embodiment, the at least one unified information unit includes atleast one built-in unified information unit that is built in thepersonal workspace and/or at least one plugged-in unified informationunit that is plugged in the personal workspace.

In an embodiment, the working environment of the personal workspaceincludes a microkernel to host the at least one information importer,the at least one unified information unit and/or the at least oneunified tool.

In an embodiment, the microkernel provides the at least one informationimporter, the at least one unified information unit and/or the at leastone unified tool to the personal workspace via the unified script,wherein the unified script is used as an intermediate language.

In an embodiment, the unified script is declared by a document typedefinition (DTD), an extensible markup language (XML) Schema, astructured language or a structured protocol.

In an embodiment, a preset unified tool for supporting the at least oneunified information unit is chosen to access or control the at least oneunified information unit by the processing unit according to theattributes of the at least one unified information unit via the personalworkspace.

In an embodiment, when a specified unified information unit of the atleast one unified information unit is dragged and dropped into thecorresponding unified tool of the at least one unified tool, thespecified unified information unit is accessible or controllable by thecorresponding unified tool. Alternatively, when a specified unified toolof the at least one unified tool is dragged and dropped into thecorresponding unified information unit of the at least one unifiedinformation unit, the corresponding unified information unit isaccessible or controllable by the specified unified tool.

In an embodiment, each of the first information source and the secondinformation source includes an internet service, a storage medium of anon-transitory computer or a storage medium of a mobile device, and/orthe original information includes a file, a web page, a database row, apolicy or a rule, and/or the original tool includes a utility, a widget,an intelligent agent, an application or a service.

In an embodiment, the at least one unified information unit includes ametadata of the at least one unified tool.

In accordance with another aspect of the present invention, there isprovided a system for combining unified matters in a personal workspace.The system includes a processing unit for arranging at least onematterizer in a personal workspace and generating at least one unifiedinformation unit and at least one unified tool through the at least onematterizer. The at least one unified information unit and the at leastone unified tool are hosted by a working environment of the personalworkspace. The at least one matterizer acquires an attribute and anassociated link of an original information from a first informationsource and models the original information into a corresponding unifiedinformation unit with a first unified data model by re-organizing theattribute and the associated link of the original information. The atleast one matterizer acquires an attribute and an associated link of anoriginal tool from a second information source and models the originaltool into the corresponding unified tool with a second unified datamodel by re-organizing the attributes and the associated link of theoriginal tool. If the original tool is compatible with the workingenvironment of the personal workspace, the corresponding unified tool isdirectly produced according to the attribute and the associated link ofthe original tool. If the original tool is incompatible with the workingenvironment of the personal workspace, the unified tool is indirectlyproduced via an adapter and/or a software development kit (SDK) of thecorresponding original tool to drive the original tool. The adapterprovides an interface implementation compatible with the personalworkspace. The processing unit accesses or controls the at least oneunified information unit to perform a task through the at least oneunified tool. When the at least one unified tool of the personal toolaccesses or controls the at least one unified information unit toperform the task, the at least one corresponding original tool accessesor controls the at least one corresponding original information.

In an embodiment, the at least one matterizer is arranged in thepersonal workspace by the processing unit via a unified script, and theunified script is used as an intermediate language in the personalworkspace.

In an embodiment, the unified script is declared by a document typedefinition (DTD), an extensible markup language (XML) Schema, astructured language or a structured protocol.

In an embodiment, the personal workspace includes a microkernel, and theat least one matterizer, the at least one unified information unitand/or the at least one unified tool is provided to the personalworkspace via a unified script, wherein the unified script is used as anintermediate language in the personal workspace.

In an embodiment, a preset unified tool for supporting the at least oneunified information unit is chosen to access or control the at least oneunified information unit by the processing unit according to theattributes of the at least one unified information unit via the personalworkspace.

In an embodiment, when a specified unified information unit of the atleast one unified information unit is dragged and dropped into thecorresponding unified tool of the at least one unified tool, thespecified unified information unit is accessible or controllable by thecorresponding unified tool. Alternatively, when a specified unified toolof the at least one unified tool is dragged and dropped into thecorresponding unified information unit of the at least one unifiedinformation unit, the corresponding unified information unit isaccessible or controllable by the specified unified tool.

In an embodiment, each of the first information source and the secondinformation source includes an internet service, a storage medium of anon-transitory computer or a storage medium of a mobile device, and/orthe original information includes a file, a web page, a database row, apolicy or a rule, and/or the original tool includes a utility, a widget,an intelligent agent, an application or a service.

In an embodiment, the at least one unified information unit includes ametadata of the at least one unified tool.

In accordance with another aspect of the present invention, there isprovided a method for combining unified matters in a personal workspace.Firstly, at least one matterizer is provided to the personal workspacevia a unified script. The at least one matterizer models a firstoriginal tool of a first information source into a first unified tool,so that basic attributes of the first unified tool include a type of thefirst original tool and a link indicating where the first original toolis located. The at least one matterizer models a second original tool ofa second information source into a second unified tool, so that basicattributes of the second unified tool include a type of the secondoriginal tool and a link indicating where the second original tool islocated. Then, the first unified tool and the second unified tool areprovided to the personal workspace. The first original toolcorresponding to the first unified tool and the second original toolcorresponding to the second unified tool are integrated with acommunication interface of a software development kit (SDK) that isprovided by the personal workspace. When a task is performed through thefirst unified tool and the second unified tool in the personalworkspace, the first original tool and the second original toolcommunicate with each other through the communication interface.

In an embodiment, the first original tool and the second original toolcommunicate with each other about an event content, a data content or aprotocol content.

In an embodiment, the unified script is used as an intermediate languagein the personal workspace.

In an embodiment the working environment of the personal workspaceincludes a microkernel to host the first unified tool and/or the secondunified tool.

In an embodiment, the microkernel provides the first unified tool andthe second unified tool to the personal workspace via the unifiedscript, wherein the unified script is used as an intermediate language.

In an embodiment, the unified script is declared by a document typedefinition (DTD), an extensible markup language (XML) Schema, astructured language or a structured protocol.

In accordance with another aspect of the present invention, there isprovided a method for combining unified matters in a personal workspace.Firstly, a matterizer is provided to the personal workspace via aunified script. The matterizer models an original tool of an informationsource into a unified tool, so that basic attributes of the unified toolinclude a type of the original tool and a link indicating where theoriginal tool is located. Then, the unified tool is provided to thepersonal workspace via the matterizer. The unified tool includes aspontaneous driving unit. When the unified tool in the personalworkspace is accessed or controlled, the spontaneous driving unit isenabled and the unified tool is automatically executed to perform atask.

In an embodiment, the unified script is used as an intermediate languagein the personal workspace.

In an embodiment, a working environment of the personal workspaceincludes a microkernel to host the first unified tool and/or the secondunified tool.

In an embodiment, the microkernel provides the unified tool to thepersonal workspace via the unified script, wherein the unified script isused as an intermediate language.

In an embodiment, the unified script is declared by a document typedefinition (DTD), an extensible markup language (XML) Schema, astructured language or a structured protocol.

The above objects and advantages of the present invention will becomemore readily apparent to those ordinarily skilled in the art afterreviewing the following detailed description and accompanying drawings,in which:

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating an implementation concept ofa unifying method according to an embodiment of the present invention;

FIG. 2 is a flowchart illustrating a method for combining unifiedmatters in a personal workspace according to a first embodiment of thepresent invention;

FIG. 3 is a schematic diagram illustrating an implementation concept ofproviding at least one matterizer to a personal workspace in the stepP11 of FIG. 2 via a unified script;

FIG. 4 is a schematic diagram illustrating an implementation concept ofallowing the unified tool corresponding to the original tool to beprovided to (e.g., built in or plugged in) the personal workspace in thestep P12 of FIG. 2;

FIG. 5 is a schematic diagram illustrating an implementation concept ofarranging the unified information units and the unified tools in thepersonal workspace according to an embodiment of the present invention;

FIG. 6 is a schematic diagram illustrating an implementation concept ofimplementing the step P13 of FIG. 2;

FIG. 7 is a schematic block diagram illustrating a computer programproduct using the method of FIG. 2;

FIG. 8 is a schematic block diagram illustrating a system for performingthe method of FIG. 2 according to an embodiment of the presentinvention;

FIG. 9 is a schematic block diagram illustrating a system for performingthe method of FIG. 2 according to another embodiment of the presentinvention;

FIG. 10 is a flowchart illustrating a method for combining unifiedmatters in a personal workspace according to a second embodiment of thepresent invention;

FIG. 11 is a schematic diagram illustrating an implementation concept ofcommunicating the first original tool corresponding to the first unifiedtool with the second original tool corresponding to the second unifiedtool through the communication interface of the software development kitto perform a task in the method of FIG. 10;

FIG. 12 is a flowchart illustrating a method for combining unifiedmatters in a personal workspace according to a third embodiment of thepresent invention;

FIG. 13 is a schematic diagram illustrating a workspace for performingthe method of FIG. 12 and a unified tool in the personal workspace;

FIG. 14 is a schematic diagram illustrating an implementation concept ofa unifying method according to another embodiment of the presentinvention; and

FIG. 15 is a schematic diagram illustrating an implementation concept ofallowing the unified tool corresponding to the original tool to beprovided to the personal workspace in the step P12 of FIG. 2 accordingto the unifying method of FIG. 14.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The present invention is more fully appreciated by reference to thefollowing description, including the following glossary of terms and theconcluding examples. For the sake of brevity, the disclosures of thepublications, including patents, cited in this specification are hereinincorporated by reference.

The examples below are non-limiting and are merely representative ofvarious aspects and features of the present invention. The term“information source” used herein is defined as a sequence of symbolsthat can be interpreted as a message in the most limited technicalmeaning. And the message is used for organizing and labelinginformation. For example, the information source includes website (suchas internet service), intranet, social network, software, electronicbook, database and other media of information (such as a storage mediumof a non-transitory computer or a storage medium of a mobile device).The term “original information” used herein is a file, a webpage, adatabase row, a policy, a rule or any data accessible in correspondingmachines and servers, but is not limited thereto. The term “originaltool” used herein is a utility, a widget, an intelligent agent, anapplication, a service or any executable component accessible incorresponding machines and servers, but is not limited thereto. It isnoted that the information sources, the original information and theoriginal tool are not restricted to the above examples.

Moreover, “original information” and “original tool” are implementationexamples of “original matters” used herein. In accordance with thepresent invention, a plurality of “original matters” from identical ordifferent “information sources” are modeled to a plurality of “unifiedmatters” by a unifying method. Consequently, the “unified matters” inthe same execution environment are compatible with each other andcooperate to perform a specified task. The “unified tool” and the“unified information unit” are implementation examples of the “unifiedmatters”. Moreover, the term “Matterizer” used herein is a means, adevice or a program code to perform the unifying process.

In an embodiment, the above unifying method comprises steps of: modelingat least one original information obtained from at least one informationsource of multiple information sources into a unified information unitwith one unified data model via re-organizing the original information,and/or modeling at least one original tool obtained from at least oneinformation source of multiple information sources into a unified toolwith another unified data model via re-organizing the original tool. Theinformation sources for every two original information units may beidentical or different. The information sources for every two originaltools may be identical or different. The information source for anyoriginal information and the information source for any original toolmay be identical or different. The one unified data model and anotherunified data model could be identical or different, and the unifyingmethod described above could be completed through a matterizer.

Please refer to FIG. 1. FIG. 1 is a schematic diagram illustrating animplementation concept of a unifying method according to an embodimentof the present invention. As shown in FIG. 1, the matterizer 992re-organizes an attribute and a link of an original matter 991 with aunified data model 993, and thus models the original matter 991 into aunified matter 994. Consequently, the basic attributes of the unifiedmatter 994 include a type of the original matter 994 and a linkindicating where the original matter 994 is located.

In this embodiment, the original matter 991 at least includes anoriginal information (not shown) or an original tool (not shown), but isnot limited thereto. The basic attributes of the unified informationunit include a type of the original information and a link indicatingwhere the original information is located. The basic attributes of theunified tool include a type of the original tool and a link indicatingwhere the original tool is located. In the above unifying method, if theattributes accessible from the original information correspond to theattributes to be unified in the unified information unit, the unifiedinformation unit is directly produced through the matterizer 992. If theattributes accessible from the original information do not correspond tothe attributes to be unified in the unified information unit, theoriginal information is firstly re-defined by logically re-organizingthe attributes and the link of the original information, and then theoriginal information is converted into a new original information withthe attributes which correspond to attributes to be unified in theunified information unit. Consequently, the unified information unit isindirectly produced.

Moreover, if the original tool is compatible with the workingenvironment of the workspace, the unified tool is directly produced bythe matterizer 992. On the other hand, if the original tool isincompatible with the working environment of the workspace, the unifiedtool is indirectly produced via an adapter and/or a software developmentkit (SDK) of the original tool to drive the original tool. The adapterprovides an interface implementation compatible with the workingenvironment.

Herein, “the descriptions of the unifying method”, “the methods ofobtaining the unified matters” and “the descriptions of the matterizer”may be referred to the U.S. patent application Ser. No. 14/324,069,entitled “A method of unifying information and tool from a plurality ofinformation sources”, and also referred to the China Patent ApplicationNo. 201410768564.X, which claims the benefit of priority to the U.S.patent application Ser. No. 14/324,069 and is entitled “A method ofunifying information and tool from a plurality of information sourcesand computer product and device using the method”. The detaileddescriptions thereof are omitted.

The above unifying method is presented herein for purpose ofillustration and description only. The method of unifying a plurality oforiginal matters from different information sources is not restricted.However, those skilled in the art will readily observe that numerousmodifications and alterations may be made while retaining the teachingsof the invention.

Hereinafter, two other unifying methods will be illustrated. The firstunifying method is applied to a method of unifying the information ofGarmin satellite navigation. Through a point-of-interest (POI) functionof the Garmin satellite navigation, the method of unifying theinformation is employed to unify the imported original point information(i.e., an original information) into the corresponding unified pointinformation (i.e., a unified information unit). The second unifyingmethod is applied to a method of unifying the tool of an Android system.The Android system is a Linux-based open source mobile operating system.However, most application programs (i.e., original tools) are written inthe Java programming language. Consequently, the application program(i.e., the original tool) written in the Java programming language canbe modeled into a unified application program (i.e., the unified tool)compatible with the Android system so as to be executed in the Androidsystem.

A method of providing a user-orientated personal workspace for a userwill be illustrated as follows. FIG. 2 is a flowchart illustrating amethod for combining unified matters in a personal workspace accordingto a first embodiment of the present invention. The method 100 comprisesthe following steps. In a step P11, at least one matterizer is providedto a personal workspace, wherein at least one unified information unitcorresponding to at least one original information and/or at least oneunified tool corresponding to at least one original tool is acquiredfrom at least one information source via the at least one matterizer. Ina step P12, the at least one unified information unit and/or the atleast one unified tool is provided to the personal workspace via the atleast one matterizer. In a step P13, a task is performed through the atleast one unified tool and/or the at least one unified information unit.

First of all, a unified script as an intermediate language for realizingthe present invention is edited. The matterizers with convertingfunctions of different formations are allowed to be provided to (e.g.,built in or plugged in) the unified script. The converting function canconvert the original information from different information sources intothe unified information unit and convert the original tool fromdifferent information sources into the unified tool. Preferably but notexclusively, the unified script is declared by a document typedefinition (DTD), an extensible markup language (XML) Schema, astructured language or a structured protocol. The matterizer can beimplemented as Java Bean, COM, or any kind of pluggable componentarchitecture. Hereinafter, information importers such as the informationimporter 23 of Dropbox 22 (see FIG. 3) and the information importer 26of Google Drive 25 (see FIG. 3) and the information importer 33 (seeFIG. 4) are some examples of the matterizer.

Moreover, according to different tasks, the at least one requiredunified information unit and/or the at least one required unified toolfrom the corresponding information source can be collected into thepersonal workspace. The unified information unit and/or the unified toolis obtained from a part or the entire of a plurality of informationsources and then modeled. Moreover, the working environment of thepersonal workspace comprises a microkernel to host the matterizer, theunified information unit and the unified tool. The microkernel canprovide the matterizer, the unified information unit or the unified toolto the projected workspace via the unified script.

FIG. 3 is a schematic diagram illustrating an implementation concept ofproviding at least one matterizer to a personal workspace in the step P1of FIG. 2 via a unified script. As shown in FIG. 3, the unified script24 is used as an intermediate language in the personal workspace 21.Moreover, the information importer 23 of Dropbox 22 and the informationimporter 26 of Google Drive 25 are configurable through the unifiedscript 24. After a unifying process, the information importer 23 ofDropbox 22 and the information importer 26 of Google Drive 25 areallowed to enter together into the same personal workspace 21.

In this embodiment, the information source in the personal workspace 21is Dropbox 22, and the information importer 23 of Dropbox 22 is asoftware component capable of unifying the information of Dropbox 22into the unified information unit. The Dropbox matterizer isconfigurable through the unified script 24, and may be one of sourceproviders for the personal workspace 21.

Moreover, another information source in the personal workspace 21 isGoogle Drive 25, and the information importer 26 of Google Drive 25 is asoftware component capable of unifying the information of Google Drive25 into the unified information unit. Similarly, the Google Drivematterizer is configurable through the unified script 24, and may be oneof source providers for the personal workspace 21.

As mentioned above, the required unified information units and/or therequired unified tools from the corresponding information sources can becollected into the personal workspace according to different tasks. Theoriginal tools are classified into compatible tools and incompatibletools. If the original tool is the compatible tool, the original toolacquired from the at least one information source is directly providedto (e.g., built in or plugged in) the personal workspace via the unifiedscript. Whereas, if the original tool is the incompatible tool, theoriginal tool acquired from the at least one information source isindirectly provided to (e.g., built in or plugged in) the personalworkspace via a compatible adapter and the unified script. Moreover,both of the compatible tool and the incompatible tool are regarded asunified tools.

FIG. 4 is a schematic diagram illustrating an implementation concept ofallowing the unified tool corresponding to the original tool to beprovided to (e.g., built in or plugged in) the personal workspace in thestep P12 of FIG. 2. First of all, the condition that the original toolis the compatible tool will be described. As shown in FIG. 4, oneoriginal tool is a Unified Calculator tool 32 in an information source.Since the component interface of the Unified Calculator tool 32 iscompatible with the component architecture for the unified tool in apersonal workspace 31, it is supposed that the Unified Calculator tool32 is a compatible unified tool and the Unified Calculator tool 32 witha specific function is able to be directly provided to (e.g., built inor plugged in) a personal workspace 31 via a unified script (i.e.,through an information importer 33).

Next, the condition that the original tool is the incompatible tool willbe described. As shown in FIG. 4, another original tool is a MicrosoftWord tool 35 in another information source. Since the componentinterface of the Microsoft Word tool 35 is incompatible with thecomponent architecture for the unified tool in the personal workspace31, an adapter 36 compatible with the component architecture for theunified tool in the personal workspace 31 is required. Then, theincompatible Microsoft Word tool 35 with a specific function is able tobe directly provided to (e.g., built in or plugged in) a personalworkspace 31 via a unified script (i.e., through a compatibleinformation importer 36 and an information importer 37). As mentioned inFIG. 4, both of the compatible tool and the incompatible tool can beunified into the same personal workspace 31 in order to perform aspecified task.

In an embodiment, the matterizer to be provided to the personalworkspace is a built-in matterizer that is added to the personalworkspace in a built-in manner, for example the matterizer that ispreviously edited into the unified script and added to the personalworkspace during the process of opening the personal workspace (e.g.,regarded as a preset matterizer). Alternatively, in another embodiment,the matterizer to be provided to the personal workspace is a plug-inmatterizer that is added to the personal workspace in a plug-in manner,for example another matterizer that is added to the personal workspacethrough the preset matterizer after the personal workspace is opened. Inparticular, in an embodiment, any matterizer can be regarded as aunified tool. That is, the matterizer is present in the personalworkspace in the form of the unified tool.

Similarly, the unified information unit to be provided to the personalworkspace is a built-in unified information unit that is added to thepersonal workspace in a built-in manner, for example the unifiedinformation unit that is previously edited into the unified script andadded to the personal workspace during the process of opening thepersonal workspace (e.g., regarded as a preset unified information unitand provided to the personal workspace through the correspondingmatterizer). Alternatively, the unified information unit to be providedto the personal workspace is a plug-in unified information unit that isadded to the personal workspace in a plug-in manner, for example theunified information unit that is added to the personal workspace throughthe corresponding matterizer after the personal workspace is opened.

Similarly, the unified tool to be provided to the personal workspace isa built-in unified tool that is added to the personal workspace in abuilt-in manner, for example the unified tool that is previously editedinto the unified script and added to the personal workspace during theprocess of opening the personal workspace (e.g., regarded as a presetunified tool and provided to the personal workspace through thecorresponding matterizer). Alternatively, the unified tool to beprovided to the personal workspace is a plug-in unified tool that isadded to the personal workspace in a plug-in manner, for example theunified tool that is added to the personal workspace through thecorresponding matterizer after the personal workspace is opened.

In another embodiment, before the step P11 of FIG. 2, the method furthercomprises a step of providing the at least one unified information unitand/or the at least one unified tool to a built-in information source ofthe at least one information source. The above unified script is anexample of the built-in information source. Consequently, the unifiedinformation unit provided to the unified script before the step P11 isregarded as the built-in unified information unit (or the preset unifiedinformation unit), and the unified tool provided to the unified scriptbefore the step 110 is regarded as the built-in unified tool (or thepreset unified tool).

Moreover, the above unified information unit may include a metadata ofthe unified tool. The example of the metadata will be illustrated asfollows. It is noted that example of the metadata is not restricted. Forexample, via the matterizer 992 of FIG. 1 (corresponding to theinformation importer 33 of FIG. 4), the Unified Calculator tool 32 ofFIG. 4 is modeled to the following profile according to a unified datamodel 993 thereof. This profile may be regarded as the metadata of theunified tool corresponding to the Unified Calculator tool 32.

{ “type”:“tool/widget”, “link”:“The url to access Unified Calculator” }

Moreover, any application program product shown on the APP store (AppleComputer, Inc.) before loading to the electronic device (e.g., a mobilephone or a tablet computer) of the user may be regarded as the metadatacorresponding to the application program product.

In an embodiment, the personal workspace is equipped with a plurality ofunified tools. Moreover, the functional feature provided by each unifiedtool can display or interpret a specified unified information unit. Thatis, after the at least one original tool is unified into the unifiedtool via the unified script, a task can be accomplished by using atleast one unified tool to process the corresponding unified informationunit. In addition, when discussing the representation of the unifiedtool of the present invention, a recognizable icon or a visible objectcan be used for remarking its operable function. An example of theunified tool includes but is not limited to a card icon, and eachunified tool has a specific function.

In an embodiment, the unified information units and the unified toolsadded to the personal workspace can be arranged by the user. FIG. 5 is aschematic diagram illustrating an implementation concept of arrangingthe unified information units and the unified tools in the personalworkspace according to an embodiment of the present invention. As shownin FIG. 5, the unified information units include Work Notes.docx 42 fromGoogle Drive (i.e., an information source) and Life Notes.docx 43 fromDropbox (i.e., an information source), and the unified tools include aDoc Viewer tool 44 from Google (i.e., an information source) and a DocViewer tool 45 from Microsoft (i.e., an information source). Moreover,as shown in FIG. 5, the user groups and places the unified informationunits and the unified tools in a specific area of the personal workspace41 in the arranging process.

Then, the step P13 of FIG. 2 will be illustrated. Moreover, according tothe operational relationship between the unified tool and the unifiedinformation unit (e.g., the clicking or dragging actions between thetwo), the user can perform a specified task by using the unified tool toaccess or control the corresponding unified information unit. When theunified tool in the personal workspace accesses or controls thecorresponding unified information unit to perform the specified task,the corresponding original tool accesses or controls the correspondingoriginal information.

Hereinafter, the process of implementing the step P13 of FIG. 2 will beillustrated with reference to FIG. 6. FIG. 6 also illustrates animplementation concept of processing the unified information unit withthe unified tool and the interaction between the unified tool and theunified information unit according to an embodiment of the presentinvention. As shown in FIG. 6, the unified information units includeWork Notes.docx 52 from Google Drive (i.e., an information source) andLife Notes.docx 53 from Dropbox (i.e., an information source), and theunified tools include a Doc Viewer tool 54 from Google (i.e., aninformation source) and a Doc Viewer tool 55 from Microsoft (i.e., aninformation source).

If the user intends to view at least one unified information unit (e.g.,Work Notes.docx 52 from Google Drive and/or Life Notes.docx 53 fromDropbox), the corresponding unified tool (e.g., the Doc Viewer tool 54from Google and/or the Doc Viewer tool 55 from Microsoft) is necessarilyintroduced into a personal workspace 51. Then, some view actions in thepersonal workspace 51 are thus associated with clicking or draggingactions.

The relationships between the view actions and the clicking actions willbe illustrated as follows. In an embodiment, the user may directly clickone unified information unit and select a supporting unified tool in thepersonal workspace 51 for viewing the clicked file upon the clicked fileattribute. For example, if the user clicks Work Notes.docx 52 andselects the Doc Viewer tool 54 in the personal workspace 51, the usercan view Work Notes.docx 52. In another embodiment, for viewing theexpected original information, several dragging actions between theunified information unit and the unified tool can be set up.

The relationships between the view actions and the dragging actions willbe illustrated as follows. In a first condition, the unified informationunit to be accessed or controlled is dragged and dropped into thecorresponding unified tool, so that the unified information unit isaccessible or controllable. For example, after the user drags WorkNotes.docx 52 and drops the same into the Doc Viewer tool 54 in thedirection indicated by the arrow D1, the user can view Work Notes.docx52. In a second condition, the unified tool for accessing or controllingthe unified information unit is dragged and dropped into the unifiedinformation unit to be accessed or controlled, so that the unifiedinformation unit is accessible or controllable. For example, after theuser drags Life Notes.docx 53 and drops the same into the Doc Viewertool 55 in the direction indicated by the arrow D2, the user can viewLife Notes.docx 53.

When the above unified tool (e.g., the Doc Viewer tool 54 from Googleand/or the Doc Viewer tool 55 from Microsoft) accesses or controls thecorresponding unified information unit (e.g., Work Notes.docx 52 fromGoogle Drive and/or Life Notes.docx 53 from Dropbox), the correspondingoriginal tool accesses or controls the corresponding originalinformation. For example, the original tool includes a non-unified DocViewer tool in the Google server and/or a non-unified Doc Viewer tool inthe Microsoft server, and the original information includes anon-unified Work Notes.docx in Google Drive and/or a non-unified LifeNotes.docx in Dropbox.

In an embodiment, during the process of operating the personal workspaceor during the process of performing the task, the user can add or deleteat least one unified information unit in the personal workspace and/orload or unload at least one unified tool in the personal workspace so asto meet the user's requirement. Moreover, if any, the features of someunified tools and the unified information units can be combined into asoftware package. Thus, it is easier for the user to perform specifictasks, for example the tasks of searching/completing the contents of thefiles in a particular project.

FIG. 7 is a schematic block diagram illustrating a computer programproduct using the method of FIG. 2. For example, the computer programproduct 62 is a software package. The computer program product 62 isused for performing a task in a personal workspace. Moreover, thecomputer program product 62 contains a program code 63. The program code71 can perform the method of FIG. 2 while the computer program product 7is executed in a computer 6. The method comprises steps of allowing atleast one matterizer, at least one unified information unitcorresponding to at least one original information and/or at least oneunified tool corresponding to at least one original tool to be providedto the personal workspace via a unified script, and performing a task byusing the at least one unified tool and/or the at least one unifiedinformation unit. The implementations of these steps are similar tothose mentioned above, and the detailed descriptions thereof areomitted.

FIG. 8 is a schematic block diagram illustrating a system for performingthe method of FIG. 2. As shown in FIG. 8, the system 81 comprises aprocessing unit 811. The processing unit 811 is used for arranging atleast one matterizer in a personal workspace and generating at least oneunified information unit and at least one unified tool through the atleast one matterizer. Moreover, the processing unit 811 uses the atleast one unified tool to access or control the at least one unifiedinformation unit so as to perform a task. In an embodiment, each of theat least one matterizer is a built-in matterizer. Moreover, each of theat least one unified tool and each of the at least one unifiedinformation unit are plugged-in unified tool and plugged-in unifiedinformation unit that are plugged in the personal workspace through theat least one matterizer. The operations of the system 81 are similar tothose mentioned above, and the detailed descriptions thereof areomitted.

FIG. 9 is a schematic block diagram illustrating a system for performingthe method of FIG. 2 according to another embodiment of the presentinvention. The system 82 comprises a processing unit 821. The processingunit 821 is used for arranging at least one information importer and atleast one unified tool in a personal workspace and providing at leastone unified information unit to the personal workspace through the atleast one information importer. Moreover, the processing unit 821 usesthe at least one unified tool to access or control the at least oneunified information unit so as to perform a task. In an embodiment, eachof the at least one information importer is a built-in importer, andeach of the at least one unified tool is a built-in unified tool.Moreover, each of the at least one unified information unit is aplugged-in unified information unit that is plugged in the personalworkspace through the at least one information importer. The operationsof the system 82 are similar to those mentioned above, and the detaileddescriptions thereof are omitted.

FIG. 10 is a flowchart illustrating a method for combining unifiedmatters in a personal workspace according to a second embodiment of thepresent invention. The method 101 comprises the following steps. In astep P21, at least one matterizer is provided to a personal workspace,wherein a first unified tool corresponding to a first original tool isacquired from a first information source via the at least onematterizer, a second unified tool corresponding to a second originaltool is acquired from a second information source via the at least onematterizer, and the first original tool corresponding to the firstunified tool and the second original tool corresponding to the secondunified tool are integrated with a communication interface of a softwaredevelopment kit (SDK) that is provided by the personal workspace. In astep P22, the first unified tool and the second unified tool areprovided to the personal workspace through the at least one matterizer.In a step P23, a task is performed through the first unified tool andthe second unified tool, wherein when the task is performed through thefirst unified tool and the second unified tool, the first original toolcorresponding to the first unified tool and the second original toolcorresponding to the second unified tool communicate with each otherthrough the communication interface of the software development kit.

FIG. 11 is a schematic diagram illustrating an implementation concept ofcommunicating the first original tool corresponding to the first unifiedtool with the second original tool corresponding to the second unifiedtool through the communication interface of the software development kitto perform a task in the method of FIG. 10. As shown in FIG. 11, a firstoriginal tool 71 of a first information source 75 and a second originaltool 72 of the second information source 76 are integrated with acommunication interface 771 of a software development kit 77 that isprovided by a personal workspace 70. Moreover, a first unified tool 73corresponding to the first original tool 71 and a second unified tool 74corresponding to the second original tool 72 are provided to thepersonal workspace 70 through at least one matterizer (not shown). Forperforming a task, the first unified tool 73 intends to communicate withthe second unified tool 74 about an event content, a data content or aprotocol content. Meanwhile, the event content, the data content or theprotocol content is transmitted from the first unified tool 73 to theworking environment of the personal workspace 70 through thecommunication interface 771. Then, the event content, the data contentor the protocol content is transmitted from the working environment ofthe personal workspace 70 to the second unified tool 74 through thecommunication interface 771. In other words, when the task is performedthrough the first unified tool 73 and the second unified tool 74, thefirst original tool 71 corresponding to the first unified tool 73 andthe second original tool 72 corresponding to the second unified tool 74communicate with each other through the communication interface 771 ofthe software development kit 77.

In an embodiment, the working environment of the personal workspace 70is implemented through html5. Moreover, for executing the first unifiedtool 73 and the second unified tool 74, an inline frame (iframe) in theworking environment of the personal workspace 70 is opened. In theworking environment of the personal workspace 70, the communicationinterface 771 of the software development kit 77 is used to exchangedata between the first original tool 71, the second original tool 72 andthe working environment through a PostMessage function. Moreover, thesoftware development kit 77 also defines an exchange protocol forhandling exchange process. Preferably but not exclusively, the exchangeprotocol defines the parameter format and the data format according tothe exchange process of the communication interface.

While the first original tool 71 corresponding to the first unified tool73 and the second original tool 72 corresponding to the second unifiedtool 74 are respectively loaded into two inline frames of the workingenvironment of the personal workspace 70, the event content, the datacontent or the protocol content can be transmitted from the firstoriginal tool 71 to the second original tool 72. That is, the eventcontent, the data content or the protocol content is packed withexchange protocol transmitted from the first unified tool 73 to theworking environment of the personal workspace 70 through thecommunication interface 771 according to the exchange process of thecommunication interface 771. For example, the data is packed with theparameter format and data format defined by the exchange protocol andexchanged through the PostMessage function. Then, the event content, thedata content or the protocol content is packed with exchange protocoland transmitted from the working environment of the personal workspace70 to the second unified tool 74 through the communication interface 771according to the exchange process of the communication interface 771.For example, the data is packed with the parameter format and dataformat defined by the exchange protocol and exchanged through thePostMessage function. Consequently, the second original tool 72 canreceive the event content, the data content or the protocol content.

As mentioned above, the data exchange for the communication interface771 of the software development kit 77 is implemented through thePostMessage function. Moreover, the working environment of the personalworkspace 70 is used as a transfer medium of the event content, the datacontent or the protocol content. The transferring computation may beexecuted by the working environment or a specified software module ofthe working environment. Moreover, the data exchange and the exchangeprotocol/exchange process of the communication interface 771 of thesoftware development kit 77 may be defined through texts, e.g., througha document. Alternatively, the communication interface 771 is providedthrough a library containing the complete implementation of the dataexchange and the exchange protocol/exchange process to reduce complexityof system integration task. The above examples are presented herein forpurpose of illustration and description only. In case that the workingenvironment of the personal workspace 70 and the executing environmentof the unified tool are different, the communication methods of the dataexchange between the first unified tool 73, the second unified tool 74and the working environment of the personal workspace 70 may bedifferent. For example, the communication interface may be implementedthrough socket, android, intent, ios url scheme, or the like.

FIG. 12 is a flowchart illustrating a method for combining unifiedmatters in a personal workspace according to a third embodiment of thepresent invention. The method 102 comprises the following steps. In astep P31, a matterizer is provided to a personal workspace, wherein aunified tool corresponding to an original tool is acquired from aninformation source via the matterizer, and the unified tool comprises aspontaneous driving unit. In a step P32, the unified tool is provided tothe personal workspace via the matterizer. In a step P33, a task isperformed through the unified tool, wherein when the unified tool isaccessed or controlled, the spontaneous driving unit is enabled and theunified tool is automatically executed to perform the task.

FIG. 13 is a schematic diagram illustrating a workspace for performingthe method of FIG. 12 and a unified tool in the personal workspace. Asshown in FIG. 13, the unified tool 57 provided to the personal workspace56 can be spontaneously driven. For example, the unified tool 57 is atool with a game property. The unified tool 57 comprises a spontaneousdriving unit 571. When the unified tool 57 is accessed or controlled(e.g., through a clicking action), the spontaneous driving unit 571 isenabled and the unified tool 57 is automatically executed.

Another unifying method as shown in FIG. 14 will be illustrated asfollows. The unified matter obtained by this unifying method can be alsoapplied to the method of FIG. 2. Please refer to FIGS. 14 and 15. FIG.15 is a schematic diagram illustrating an implementation concept of aunifying method according to another embodiment of the presentinvention. FIG. 14 is a schematic diagram illustrating an implementationconcept of allowing the unified tool corresponding to the original toolto be provided to the personal workspace in the step P12 of FIG. 2according to the unifying method of FIG. 14.

As shown in FIG. 14, an original tool 995 in any language is modeledinto a unified tool 998 in a Python language via a matterizer 996according to a unified data model 997. Consequently, the process ofunifying the original tool 995 is completed. As shown in FIG. 15, theoriginal tools include a tool 92 and a tool 95. The tool 92 is obtainedfrom an information source and written in the Python language. The tool95 is obtained from another information source and written in aJavascript language. A unified script 94 is written in the Pythonlanguage. Consequently, any unified tool written in the Python languageis compatible with the component architecture for the unified tool in apersonal workspace 91. Since the tool 92 in the Python language is thecompatible tool, the tool 92 in the Python language can be directlyprovided to the personal workspace 91 via the unified script 94. Thetool 95 in the Javascript language is an incompatible tool.Consequently, after the tool 95 in the Javascript language isdynamically compiled as the Python structure via an adapter 96compatible with the component architecture for the unified tool in apersonal workspace 91, the tool 95 is provided to the personal workspace91. As mentioned in FIG. 15, both of the compatible tool and theincompatible tool can be unified into the same personal workspace inorder to perform a specified task.

From the above descriptions, the present invention provides auser-orientated unified personal workspace. The present invention hasthe following advantages.

Firstly, when compared with the conventional operating system, thepersonal workspace brings no boundary in sharing different informationsources from internet. That is, the original information and theoriginal tool from different information sources are respectivelyunified into a unified information unit and a unified tool in a personalworkspace dedicated to a user, and the unified tool can be used toprocess the unified information unit for completing some specific tasks.Consequently, all of the original information and the original toolsform different information sources will be used by the user in thepersonal workspace.

Secondly, the unified information unit and the unified tool in thepersonal workspace can be interactive. That is, the unified tool isallowed to process a corresponding unified information unit.

Thirdly, when an operating system is updated, other software mayencounter incompatible problems causing inconveniences to the users. Theusers are forced to learn new operating system as well as the updatedversion of software. The present invention creates a personal workspacewithout new version update problem when compared with other operatingsystems.

Fourthly, the present invention provides a user-orientated personalworkspace. That is, ideal unified information units or ideal unifiedtools are configured in the personal workspace according to thepractical requirements of the user.

Fifthly, the personal workspace is able to access and control themultiple original informations from the different information sources.

While the invention has been described in terms of what is presentlyconsidered to be the most practical and preferred embodiments, it is tobe understood that the invention needs not be limited to the disclosedembodiments. On the contrary, it is intended to cover variousmodifications and similar arrangements included within the spirit andscope of the appended claims which are to be accorded with the broadestinterpretation so as to encompass all such modifications and similarstructures.

What is claimed is:
 1. A system for processing an information unit in apersonal workspace, the system comprising a processing device and anon-transitory storage medium having program code stored therein that inresponse to execution by the processing device, causes the system to atleast: arrange a personal workspace equipped with an unified tool todisplay or interpret the information unit, wherein a data model of theinformation unit contains an attribute and/or a link indicating alocation of an original information, and the original information islocated in a first information source; represent the unified tool as arecognizable icon or visible object in the personal workspace, whereinthe unified tool is modeled from an original tool, the original tool islocated in a second information source different from the firstinformation source; and in response to an action of clicking or draggingon the information unit and/or the recognizable icon or visible object,display or interpret the information unit, and wherein the originalinformation corresponding to the information unit is accessed orcontrolled by the original tool.
 2. The system according to claim 1,wherein the information unit is produced by modeling at least one of anattribute and an associated link of the original information to theinformation unit, using the data model of the information unit.
 3. Thesystem according to claim 2, wherein the information unit is a built-ininformation unit that is built in the personal workspace and/or aplugged-in information unit that is plugged in the personal workspace.4. The system according to claim 1, wherein a working environment of thepersonal workspace comprises a microkernel to host at least oneinformation importer, at least one information unit, and/or at least oneunified tool.
 5. The system according to claim 4, wherein themicrokernel provides the at least one information importer, the at leastone information unit, and/or the at least one unified tool to thepersonal workspace via a unified script, and wherein the unified scriptis used as an intermediate language in the personal workspace.
 6. Thesystem according to claim 5, wherein the unified script is declared by adocument type definition (DTD), an extensible markup language (XML)schema, a structured language, or a structured protocol.
 7. The systemaccording to claim 1, wherein the unified tool is a preset unified toolchosen for displaying or interpreting the information unit according toone or more attributes of the information unit.
 8. The system accordingto claim 1, wherein when the information unit is dragged and droppedinto the unified tool, the information unit is accessible orcontrollable by the unified tool; or wherein when the unified tool isdragged and dropped into the information unit, the information unit isaccessible or controllable by the unified tool.
 9. The system accordingto claim 1, wherein the first information source and/or the secondinformation source is different from where the personal workspace islocated.
 10. The system according to claim 1, wherein the unified toolis produced by modeling at least one of an attribute and an associatedlink of the original tool of the second information source to theunified tool, using the data model of the unified tool.
 11. The systemaccording to claim 1, wherein each of the first information source andthe second information source includes an internet service, a storagemedium of a non-transitory computer, or a storage medium of a mobiledevice, and wherein the original information of the first informationsource includes a file, a web page, a database row, a policy, or a rule,and wherein the original tool of the second information source includesa utility, a widget, an intelligent agent, an application, or a service.12. The system according to claim 1, wherein the data model of theunified tool contains an attribute and/or a link indicating the locationof the original tool.
 13. A non-transitory storage medium for processingan information unit in a personal workspace, the non-transitory storagemedium having program code stored therein that in response to executionby a processing device, causes a system to at least: arrange a personalworkspace equipped with an unified tool to display or interpret theinformation unit, wherein a data model of the information unit containsan attribute and/or a link indicating a location of an originalinformation, and the original information is located in a firstinformation source; represent the unified tool as a recognizable icon orvisible object in the personal workspace, wherein the unified tool ismodeled from an original tool, the original tool is located in a secondinformation source different from the first information source; and inresponse to an action of clicking or dragging on the information unitand/or the recognizable icon or visible object, display or interpret theinformation unit, and wherein the original information corresponding tothe information unit is accessed or controlled by the original tool. 14.The non-transitory storage medium according to claim 13, wherein theinformation unit is produced by modeling at least one of an attributeand an associated link of the original information to the informationunit, using the data model of the information unit.
 15. Thenon-transitory storage medium according to claim 14, wherein theinformation unit is a built-in information unit that is built in thepersonal workspace and/or a plugged-in information unit that is pluggedin the personal workspace.
 16. The non-transitory storage mediumaccording to claim 13, wherein a working environment of the personalworkspace comprises a microkernel to host at least one informationimporter, at least one information unit, and/or at least one unifiedtool.
 17. The non-transitory storage medium according to claim 16,wherein the microkernel provides the at least one information importer,the at least one information unit, and/or the at least one unified toolto the personal workspace via a unified script, and wherein the unifiedscript is used as an intermediate language in the personal workspace.18. The non-transitory storage medium according to claim 17, wherein theunified script is declared by a document type definition (DTD), anextensible markup language (XML) schema, a structured language, or astructured protocol.
 19. The non-transitory storage medium according toclaim 13, wherein the unified tool is a preset unified tool chosen fordisplaying or interpreting the information unit according to one or moreattributes of the information unit.
 20. The non-transitory storagemedium according to claim 13, wherein when the information unit isdragged and dropped into the unified tool, the information unit isaccessible or controllable by the unified tool; or wherein when theunified tool is dragged and dropped into the information unit, theinformation unit is accessible or controllable by the unified tool. 21.The non-transitory storage medium according to claim 13, wherein thefirst information source and/or the second information source isdifferent from where the personal workspace is located.
 22. Thenon-transitory storage medium according to claim 13, wherein the unifiedtool is produced by modeling at least one of an attribute and anassociated link of the original tool of the second information source tothe unified tool, using the data model of the unified tool.
 23. Thenon-transitory storage medium according to claim 13, wherein each of thefirst information source and the second information source includes aninternet service, a storage medium of a non-transitory computer, or astorage medium of a mobile device, and wherein the original informationof the first information source includes a file, a web page, a databaserow, a policy, or a rule, and wherein the original tool of the secondinformation source includes a utility, a widget, an intelligent agent,an application, or a service.
 24. The non-transitory storage mediumaccording to claim 13, wherein the data model of the unified toolcontains an attribute and/or a link indicating the location of theoriginal tool.
 25. A method for processing an information unit in apersonal workspace, comprising: arranging a personal workspace equippedwith an unified tool to display or interpret the information unit,wherein a data model of the information unit contains an attributeand/or a link indicating a location of an original information, and theoriginal information is located in a first information source;representing the unified tool as a recognizable icon or visible objectin the personal workspace, wherein the unified tool is modeled from anoriginal tool, the original tool is located in a second informationsource different from the first information source; and in response toan action of clicking or dragging on the information unit and/or therecognizable icon or visible object, displaying or interpreting theinformation unit, and wherein the original information corresponding tothe information unit is accessed or controlled by the original tool. 26.The method according to claim 25, wherein the information unit isproduced by modeling at least one of an attribute and an associated linkof the original information to the information unit, using the datamodel of the information unit.
 27. The method according to claim 26,wherein the information unit is a built-in information unit that isbuilt in the personal workspace and/or a plugged-in information unitthat is plugged in the personal workspace.
 28. The method according toclaim 25, wherein a working environment of the personal workspacecomprises a microkernel to host at least one information importer, atleast one information unit, and/or at least one unified tool.
 29. Themethod according to claim 28, wherein the microkernel provides the atleast one information importer, the at least one information unit,and/or the at least one unified tool to the personal workspace via aunified script, and wherein the unified script is used as anintermediate language in the personal workspace.
 30. The methodaccording to claim 29, wherein the unified script is declared by adocument type definition (DTD), an extensible markup language (XML)schema, a structured language, or a structured protocol.
 31. The methodaccording to claim 25, wherein the unified tool is a preset unified toolchosen for displaying or interpreting the information unit according toone or more attributes of the information unit.
 32. The method accordingto claim 25, wherein when the information unit is dragged and droppedinto the unified tool, the information unit is accessible orcontrollable by the unified tool; or wherein when the unified tool isdragged and dropped into the information unit, the information unit isaccessible or controllable by the unified tool.
 33. The method accordingto claim 25, wherein the first information source and/or the secondinformation source is different from where the personal workspace islocated.
 34. The method according to claim 25, wherein the unified toolis produced by modeling at least one of an attribute and an associatedlink of the original tool of the second information source to theunified tool, using the data model of the unified tool.
 35. The methodaccording to claim 25, wherein each of the first information source andthe second information source includes an internet service, a storagemedium of a non-transitory computer, or a storage medium of a mobiledevice, and wherein the original information of the first informationsource includes a file, a web page, a database row, a policy, or a rule,and wherein the original tool of the second information source includesa utility, a widget, an intelligent agent, an application, or a service.36. The method according to claim 25, wherein the data model of theunified tool contains an attribute and/or a link indicating the locationof the original tool.